Manually entered Image API paramters is, of course, not how IIIF images are used in practice.
Once we start to see what support for the IIIF Image API can provide to software, we can unlock the power of the API.
With very high resolution images, for example, delivering the entire image to the user in their web browser is:
The IIIF Image API, makes another way possible.
Tiled deep zoom of images.
Open Seadragon is an open source javascript component that can request image tiles, that is, just small fragments of the image, at a time, to create a smooth, zooming and panning user experience, without the need for Flash or plugins.
If you use the developer tools in your browser, and look at what is happening when you zoom into the image, you'll see that the browser is only requesting just enough of the image at a time to support the panning and zooming user experience.
A typical tile might look like:
The tile size will depend on how the image server is configured, and the image server can tell (via the info.json) OpenSeadragon what size of tile request it prefers.
These standard image requests don't just support the functionality of a viewer, and I will cover viewers in more detail later, but can also be used to deliver images directly to other software or services.
For example, Google, Microsoft, Amazon and others, provide services that can do image analysis, computer vision, and text extraction.
Azure:
https://azure.microsoft.com/en-us/services/cognitive-services/computer-vision/
I could paste in a IIIF Image URI into this demonstration page and extract the text.
With IIIF I could pass the whole page, or just pass a relevant section of the page.
More on images and text later.
Or for an image with no text:
Or for a colour photograph from Harvard Art Museum:
https://ids.lib.harvard.edu/ids/iiif/10466656/full/full/0/native.jpg
We can pass this to automated tagging or image description.